Introduce Independent License Clarity Thresholds Mechanism#1689
Conversation
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
ac3b12c to
11a9116
Compare
|
Changes Made: Next Steps: |
tdruez
left a comment
There was a problem hiding this comment.
@NucleonGodX The code changes look fine in general.
Make sure to run make valid to fix the code format before a commit (currently failing the CI)
Renamed policies.py → license_policies.py.
This is out of scope and unneeded for now. Please revert this part and keep the PR focus on the "License Clarity" implementation.
If another module needs a rename, it needs to be discussed and handled separately as it may break external usage and dependencies on that module.
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
|
Thanks for the suggestions, I've applied them @tdruez |
|
@NucleonGodX LGTM!
Sounds like a plan! |
Fixes #1678
Summary of Changes
This pull request introduces a new module for managing license clarity thresholds:
About the policies.yml Structure for License Clarity Thresholds
The policies.yml file is a YAML configuration used to define various compliance policies for ScanCode.io and related tools. With these changes, a new section called license_clarity_thresholds is introduced specifically for clarity score compliance.
Example policies.yml for clarity thresholds:
Validation of threshold policy structure:
ok,warning,errorEvaluation logic for mapping clarity scores to compliance alerts (
ok,warning,error)Comprehensive test suite covering:
Note: This module is self-contained and not yet integrated into the main compliance or project logic. It is intended for review and further development.
Future Work
policies.yml